The 2-server configuration helps to separate the internal iMIS system from the public site: the public web server communicates with the iMIS database as needed, but the iMIS database stays separated from the Internet. Performance improves because spikes in traffic to the public site do not necessarily cause spikes to the iMIS database server. (The database itself will see the same traffic, but its server won't bog down with web requests.) However, internal users can still see performance issues when iMIS is under load, such as when running large reports or slow queries.
Benefits
■ Separates Public site from iMIS database
■ Better performance
Considerations
■ No redundancy
■ Given heavy internal use, performance can still suffer
■ No way to protect users from spikes in system usage (but less of an issue with robust servers)
Database server and iMIS appserver with support for Desktop and web clients on one host, and an iMIS appserver with support only for the Public view on a second host
|
Examples |
Appserver |
Database server |
|
Small |
□ 4 GB of RAM □ 2.8 GHz Dual Core Pentium or Celeron CPU □ 250 GB hard drive w/ 200 GB free |
□ 4 GB of RAM □ 2.8 GHz Dual Core Pentium or Celeron CPU □ 250 GB hard drive w/ 200 GB free |
|
Medium |
□ 4 GB of RAM □ 2.8 GHz Dual Core Pentium or Celeron CPU □ 250 GB hard drive w/ 200 GB free |
□ 6-8 GB of RAM □ 2.33 GHz Quad Core Xeon CPU, 1333MHz FSB □ 250 GB hard drive w/ 200 GB free |
|
Large |
□ 4 GB of RAM □ 2.8 GHz Dual Core Pentium or Celeron CPU □ 250 GB hard drive w/ 200 GB free |
□ 12-16 GB of RAM □ Dual 2.33 GHz Quad Core Xeon CPU, 1333MHz FSB □ 2 - 500 GB hard drive w/ 450 GB free |